Notes/Domino 6 and 7 Forum : Upgrade issue - "Database time is too far in the future"

A problem that I noticed during R6 Beta versions is still here. I "think" that I have found a fix, but am not sure of the actual cause.

I updated my existing R5 client to R6 per IBM Lotus instructions. Rebuilt all Full Text Indexes per R6 Release Notes (R5 FTIs not compatible with R6).

But some databases that worked fine in R5 started having a date/time issue in my new R6 client.

My clients Notes Log listed the problem

12/30/2002 05:38:40 PM Database (C:\Program Files\Lotus\Notes\Data\Cache.NDK) time is too far in the future.
12/30/2002 05:38:53 PM Database (C:\Program Files\Lotus\Notes\Data\log.nsf) time is too far in the future.
12/30/2002 05:38:56 PM Database (C:\Program Files\Lotus\Notes\Data\mail.box) time is too far in the future.
12/30/2002 05:38:57 PM Database (C:\Program Files\Lotus\Notes\Data\mail\wlally.nsf) time is too far in the future.

So first off, I'd advise everyone to check their individual Notes Log to see if this is happening on their client. The log is one sure fire way to find the troubled databases.

Another way is to check the date of the last Full Text Index. No matter how many times I blew it away and then recreated it, my mailfiles FTI was always dated 05/30/2003 08:03:52 PM

And as if that were not bad enough, the Replication History of my mail file started listing this same 2003 date as the last Sent time (which as you might expect, started to REALLY mess up my mail replication). I'd clear the Replication History, and rep again. Exact same thing and exact same date & time in the Replication History everytime!?!

And yes, the date and time on my computer are set properly and have not been changed in any way.

The Fix-

Deleted all local replicas listed in my log as having the future time problem. Since my log was one of the troubled DBs, I needed to jot all of these down before closing Lotus Notes to delete the log.

After re-opening Lotus Notes, I created new Replicas (my new Notes Log was created on the fly when I opened Lotus Notes).

Full Text Indexed everything that needed indexing. And "so far" everything seems to be A-OK.

One sidenote --> I wrote about this a few months ago in the R6 Beta forums, but no one else seemed to be experiencing the problem. And as a System Administrator, I have a lot of local replica databases . . . so it may just be a fluke that a few of them had this problem. But it definitely fell into the "weird" catagory!

Bill